@akien-mga @m4gr3d can you review?

Running clang-format -i <source-file> should help you fix source formatting issues :)

@naithar yes I will do it with last commit.

Looks like a solid piece of work, but... Actually, I do not see any problem to implement any third-party integrations using gdnative c++ API. It is possible since godotengine/godot-cpp#353. I've already use Appsflyer, Facebook, Firebase, Onesignal, Zendesk. Is this really needed?

Andoid modules look like a legacy as well, so we have android modules is not best argumentation.

Looks like a solid piece of work, but... Actually, I do not see any problem to implement any third-party integrations using gdnative c++ API. It is possible since godotengine/godot-cpp#353. I've already use Appsflyer, Facebook, Firebase, Onesignal, Zendesk. Is this really needed?

Andoid modules look like a legacy as well, so we have android modules is not best argumentation.

Well, GDNative doesn't give access to AppDelegate or any other platform specific code for iOS. Plugins should solve this (the other plugin system PR solved it by being actually modules that could be built separately from engine).

Well, GDNative doesn't give access to AppDelegate or any other platform specific code for iOS. Plugins should solve this (the other plugin system PR solved it by being actually modules that could be built separately from engine).

Addons can use Method Swizzling to overwrite AppDelegate methods. When you write a plugin using ObjectiveCPP there is no single point in iOS you couldn't access (I didn't meet any developing those addons). We just need better tutorials and examples with gdnative and ios.

When you write a plugin using ObjectiveCPP there is no single point in iOS you couldn't access (I didn't meet any developing those addons).

This #41230 allows plugin to directly use Godot's iOS platform code. And some wrappers could be done for this PR.
Method Swizzling is not really a good option and shouldn't be used lightly if at all.

I have added custom variable types for type check and tomorrow I will add MethodInfo like SignalInfo for type safety.

End of the development.

Why was this abruptly closed? It doesn't seem like the issue was settled, and this functionality would be useful for 3.2 users?

It's superseded by #41230 and #41340.